home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
remote
/
race152.zip
/
UPDATE.152
< prev
next >
Wrap
Text File
|
1991-11-30
|
2KB
|
55 lines
RACE version 1.52 update documentation
NOTICE!! - Please be sure to read the README.NOW file included
in the RACE v1.52 update file or full archive. This
contains very important information for registered
users.
v1.52 - FIXES/UPDATES
1: The USERSIDX.BBS file (Fast index) was not opened properly and
if SHARE was active, the index was not updated during a pack or
a sort. The result was that RemoteAccess would give an error
message and in the process it would rebuild the index, correcting
the problem.
2: The 'pHone' selection in the search menu used the same hotkey as
the 'Handle' selection. pHone has been changed to 'Telephone'.
3: RACE generated messages were given improperly delimited dates,
i.e. mm/dd/yy instead of mm-dd-yy. This apparently could cause
a problem with utils that pack the message base by date.
4: RACEEDIT has been updated to allow calling in an existing text
file for editing. ALT-I will prompt you for a filename which
you wish to edit.
NOTE! The file imported REPLACES whatever is in the editor. It
does NOT append to any existing text.
5: While I have had one report of RA not being able to find a user
after a simple edit of a user record, I have not been able to
duplicate this. In order to track this down, I have changed
the index update after a record edit. Previously, USERSIDX was
updated after ANY change to a user record. Now it (more accurately)
only updates USERSIDX if the user name or handle is changed.
6: RACE incorrectly identified its own version number upon exit. fixed.
7: Selecting a report template that had no fields selected caused an
error. Fixed.
8: Registered user key routines were completely rewritten. Be sure to
look at the README.NOW file included in the distribution archive.
v1.51 - FIXES/UPDATES
1: The user LOCATION field was incorrectly defined as allowing
35 characters. If the field was edited and entry exceeded
25 characters, the overflow ended up in the password field.